<?php
/**
 * <https://y.st./>
 * Copyright © 2018 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. If not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'<{title}>' => 'No shoes',
	'takedown' => '2017-11-01',
	'<{body}>' => <<<END
<img src="/img/CC_BY-SA_4.0/y.st./weblog/2018/04/14.jpg" alt="A grub on a stem" class="framed-centred-image" width="649" height="480"/>
<section id="drudgery">
	<h2>Drudgery</h2>
	<p>
		My discussion post for the day:
	</p>
	<blockquote>
		<p>
			I wouldn&apos;t say that Ethernet&apos;s larger packet size makes it unable to prioritise traffic well.
			Ethernet can still prioritise traffic as well as Asynchronous Transfer Mode, it&apos;s just slower to react to newly-arriving traffic.
			It has to wait until the current packet has finished transmitting to start the next packet, but Asynchronous Transfer Mode has that same issue.
			Ethernet&apos;s large packet size just means that the finish of that transfer is further away.
		</p>
		<p>
			How does Asynchronous Transfer Mode&apos;s asynchronous nature prevent wasted time on idle lines?
			Also, collisions waste bandwidth, with or without a connection.
		</p>
		<p>
			It&apos;s worth noting that while Ethernet has scalability issues, so does Asynchronous Transfer Mode.
			With each new node added, there are more potential communications going on.
			With each new connection made, every node along the connection&apos;s path has to store two table entries: one for the incoming connection and one for the outgoing one.
			This is fine for small to medium networks, but if the network gets too large, the connection tables get huge and unwieldy.
		</p>
	</blockquote>
</section>
<section id="shoes">
	<h2>Shoes</h2>
	<p>
		It turns out the non-slip shoes I got yesterday are part leather, so I wasn&apos;t able to wear them myself.
		Darn.
		I should&apos;ve checked yesterday.
		Anyway, I gave them to the first coworker that&apos;d take them off my hands today.
		It&apos;s too bad, too; they were my size and mine are falling apart a bit.
		It&apos;s probably for the best though.
		I hope to escape that place soon, and I never want to go back to food service.
		If all goes well, I wouldn&apos;t get much use out of those shoes anyway.
	</p>
</section>
END
);
